fix(frontend): resolve typecheck and lint errors - #674

🏁 Script executed:

sed -n '1,115p' apps/frontend/components/analytics/SpendChartInner.tsx
printf '\n--- Recharts declarations and package version references ---\n'
rg -n '"recharts"|TooltipProps|content=' apps/frontend package.json pnpm-lock.yaml yarn.lock package-lock.json 2>/dev/null | head -200

Repository: DelegoLabs/Delego

Length of output: 2990

🏁 Script executed:

printf '%s\n' '--- Frontend package metadata ---'
cat -n apps/frontend/package.json | sed -n '25,45p'
printf '%s\n' '--- Lockfiles containing the resolved Recharts version ---'
rg -n -C 3 'recharts@|recharts:' --glob '*lock*' --glob 'package.json' . | head -120

Repository: DelegoLabs/Delego

Length of output: 2221

🌐 Web query:

Recharts 2.15.0 Tooltip content callback type TooltipProps source

💡 Result:

In Recharts 2.15.0, the content prop for the Tooltip component is typed as ContentType<TValue, TName> [1][2]. This type allows you to pass either a React element or a function to customize the tooltip's rendering [3][2]. The ContentType is defined as follows: Type = React.ReactElement | ((props: TooltipContentProps<TValue, TName>) => React.ReactNode); When using a function (a render prop) for the content prop, it receives an object containing the tooltip's context and data (often referred to in community discussions as TooltipContentProps) [2][4]. This function should return HTML elements, not SVG elements [3][2]. If the content prop is not provided, Recharts defaults to using the internal DefaultTooltipContent component [3][2]. If a React element is passed, Recharts clones that element and injects the tooltip's props into it [3][2]. Please note that in Recharts 3.x, the internal type handling and props passed to custom content were updated, which occasionally creates confusion when referencing older 2.x documentation or community discussions [5][4][6]. For version 2.15.0 specifically, you should rely on the type definitions available in the 2.15.0 package [1][7].

Citations:

• 1: https://app.unpkg.com/recharts@2.15.0/files/types/component/Tooltip.d.ts
• 2: https://github.com/recharts/recharts/blob/fc962394/src/component/Tooltip.tsx
• 3: https://recharts.github.io/en-US/api/Tooltip/
• 4: GitHub issue 5994 in recharts/recharts (link omitted to avoid creating a cross-reference)
• 5: https://app.unpkg.com/recharts@3.10.1/files/types/component/Tooltip.d.ts
• 6: https://app.unpkg.com/recharts@3.10.0/files/types/component/Tooltip.d.ts
• 7: https://app.unpkg.com/recharts@2.15.0/files/types/component/DefaultTooltipContent.d.ts

🏁 Script executed:

python3 - <<'PY'
from urllib.request import urlopen
for version in ("2.15.0", "2.15.4"):
    url = f"https://unpkg.com/recharts@{version}/types/component/Tooltip.d.ts"
    print(f"--- recharts {version} Tooltip.d.ts ---")
    text = urlopen(url, timeout=10).read().decode()
    for i, line in enumerate(text.splitlines(), 1):
        if any(name in line for name in ("TooltipContentProps", "ContentType", "interface TooltipProps", "content?:")):
            print(f"{i}: {line}")
PY

Repository: DelegoLabs/Delego

Length of output: 2478

🏁 Script executed:

for version in 2.15.0 2.15.4; do
  echo "--- recharts $version Tooltip.d.ts ---"
  curl -fsSLk "https://unpkg.com/recharts@$version/types/component/Tooltip.d.ts" |
    grep -nE 'TooltipContentProps|ContentType|interface TooltipProps|content\?:'
done

Repository: DelegoLabs/Delego

Length of output: 611

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

🏁 Script executed:

#!/bin/bash
set -euo pipefail

node <<'NODE'
const descriptor = {
  value: null,
  writable: false,
  enumerable: false,
  configurable: true,
};

Object.defineProperty(BigInt.prototype, "toJSON", descriptor);

const original = Object.getOwnPropertyDescriptor(BigInt.prototype, "toJSON");
delete BigInt.prototype.toJSON;
// Model the current restoration.
if (original.value) BigInt.prototype.toJSON = original.value;

const restored = Object.getOwnPropertyDescriptor(BigInt.prototype, "toJSON");
console.log({ original, restored });
NODE

Repository: DelegoLabs/Delego

Length of output: 284

🏁 Script executed:

#!/bin/bash
set -euo pipefail
sed -n '70,125p' apps/frontend/lib/readModelCache.ts

Repository: DelegoLabs/Delego

Length of output: 1631

🏁 Script executed:

#!/bin/bash
set -eu
printf '%s\n' '--- changed file context ---'
sed -n '90,125p' apps/frontend/tests/setup.ts
printf '%s\n' '--- MSW dependency and handler bindings ---'
rg -n -C 3 '"msw"|setupServer|onUnhandledRequest|resetHandlers|server\.listen' apps/frontend package.json package-lock.json pnpm-lock.yaml yarn.lock 2>/dev/null || true

Repository: DelegoLabs/Delego

Length of output: 8705

🏁 Script executed:

#!/bin/bash
set -eu
printf '%s\n' '--- server and handler aggregation ---'
sed -n '1,120p' apps/frontend/mocks/server.ts
sed -n '1,180p' apps/frontend/mocks/handlers.ts 2>/dev/null || true
printf '%s\n' '--- configured API URL and representative request callers ---'
rg -n -C 3 'NEXT_PUBLIC_API_URL|fetch\(|axios|/api/|api\.example\.com' apps/frontend --glob '!**/*.test.*' --glob '!**/mocks/handlers/**' | head -240

Repository: DelegoLabs/Delego

Length of output: 16212

🌐 Web query:

MSW 2.7 setupServer onUnhandledRequest bypass error official documentation

💡 Result:

In Mock Service Worker (MSW) 2.7, the onUnhandledRequest option for server.listen defines how the server reacts when it receives a request that does not match any defined request handlers [1]. The 'bypass' strategy is a valid configuration that instructs MSW to perform the request as-is without printing any warnings or errors [1][2]. If you are encountering an error when using 'bypass', it is likely because the option is being misused or conflicting with other test configurations, as 'bypass' itself is designed specifically to suppress the standard unhandled request warnings [1][2]. To use the 'bypass' strategy, pass it to the server.listen method: server.listen({ onUnhandledRequest: 'bypass', }) If you are facing issues where an unhandled request is still causing problems, consider the following points based on official MSW documentation and best practices: 1. Understanding 'bypass' vs 'error': The 'bypass' strategy allows the request to reach the network, whereas the 'error' strategy explicitly throws an exception, which is often used in tests to ensure all requests are strictly mocked [1][3][4]. If your goal is to prevent unmocked requests, ensure you are not accidentally setting this to 'error' or using a custom callback that throws [1][5][3]. 2. Custom Strategy Callback: If you only want to bypass specific requests (e.g., static assets) while still warning or erroring on others, you can provide a function instead of a string [1][6]. This function receives the request and a print utility [1]: server.listen({ onUnhandledRequest(request, print) { if (request.url.pathname.includes('/assets/')) { return // Bypass these requests } print.warning // Warn on everything else }, }) 3. Avoiding 'bypass' in tests: The MSW maintainers strongly recommend against performing actual network requests during tests [3]. Instead of bypassing, they suggest mocking the missing endpoints (even with a 501 Not Implemented response) to keep your tests predictable and isolated [3]. If you are seeing an error message specifically mentioning an inability to bypass, verify that your testing framework is not swallowing or re-throwing errors related to MSW's internal request handling, and ensure you are using the latest version of MSW compatible with your environment [7].

Citations:

• 1: https://mswjs.io/docs/api/setup-server/listen/
• 2: GitHub discussion 1589 in mswjs/msw (link omitted to avoid creating a cross-reference)
• 3: GitHub discussion 1023 in mswjs/msw (link omitted to avoid creating a cross-reference)
• 4: https://mswjs.io/docs/best-practices/avoid-request-assertions/
• 5: GitHub discussion 874 in mswjs/msw (link omitted to avoid creating a cross-reference)
• 6: GitHub discussion 1231 in mswjs/msw (link omitted to avoid creating a cross-reference)
• 7: GitHub discussion 943 in mswjs/msw (link omitted to avoid creating a cross-reference)